Dynamic modification of a subscriber connection

ABSTRACT

In one embodiment, a method comprises receiving a request to modify a subscriber connection to a network element. The method also includes modifying attributes of the subscriber connection, within a memory of the network element, without disconnecting the subscriber connection from the network element.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 13/162,554,filed Jun. 16, 2011, which is a continuation of application Ser. No.11/980,831, filed Oct. 30, 2007, issued as U.S. Pat. No. 7,987,276,which is a continuation of application Ser. No. 10/176,222, filed Jun.20, 2002, issued as U.S. Pat. No. 7,290,054, which claims the benefit ofU.S. provisional patent application No. 60/375,684 entitled “DynamicModification of a Subscriber Connection,” filed Apr. 26, 2002, which areeach incorporated by reference.

FIELD OF THE INVENTION

The invention relates to the field of communications. More specifically,the invention relates to enabling dynamic modification of a subscriberconnection.

BACKGROUND OF THE INVENTION

In the field of communications, the need for high-speed transmission ofdata including video and audio has continued to increase. Moreover,there has been an increase in the selection of services by which userscan connect to a network, such as the Internet. Specifically, InternetService Providers (ISPs) may allow for connectivity to the Internetthrough lower-speed connections at different rates, such as 56kilobits/second, by employing a Plain Old Telephone Service (POTS) line.Other choices for connection, which are at higher speeds, into a networkcan include Integrated Services Digital Network (ISDN), DigitalSubscriber Line (DSL) service (both using a POTS line), and cable modemservice over a Radio Frequency (RF) cable line.

Additionally, there is an increasing demand by the ISPs to allow formodifications in the connection rates for a given type of service. Inparticular, the market to provide certain services, including DSL, isvery competitive. Accordingly, the low-speed connections are deeplydiscounted. Additionally, there are less users of the higher-speedconnections due to the costs. Therefore, ISPs need an approach tooffering variable services, wherein a subscriber can typically pay forlow-speed connection service, while occasionally upgrading theirconnection when a higher bandwidth may be needed and/or advantageous.

Accordingly, this enables the ISPs as well as the users of the ISPsflexibility with regard to bandwidth usage and costs associatedtherewith. To help illustrate, a given user may want to connect to theInternet at a slower connection speed when the user is only traversingpages of different web sites, in comparison to when the user may beinvolved in a video conference and/or downloading a large amount of datawherein a higher connection speed is needed and/or more advantageous.

Disadvantageously, current approaches to allow for modifications to asubscriber connection (such as modifications to the connection rate orpolicing values for the connection) to a network require that thesubscriber connection be broken, wherein a new connection isre-established that applies these modifications. Accordingly,subscribers experience service interruptions when a modification is madeto the current connection. Moreover, administrators working for the ISPscan be required to manage the updates to these subscriber accountsand/or connections.

SUMMARY OF THE INVENTION

A method and apparatus for enabling dynamic modification of a subscriberconnection are described. In one embodiment, a method comprisesreceiving a request to modify a subscriber connection to a networkelement. The method also includes modifying attributes of the subscriberconnection, within a memory of the network element, withoutdisconnecting the subscriber connection from the network element.

In an embodiment, an apparatus comprises a memory to store an attributeof a subscriber connection between a computing device and a network. Theapparatus also comprises a forwarding engine coupled to the memory. Theforwarding engine is to modify the attribute of the subscriberconnection, while the subscriber connection is active, withoutdisconnecting the subscriber connection.

In one embodiment, a network element comprises a traffic card coupled toconnect a computing device and a network through a subscriberconnection. The network element also comprises a forwarding card coupledto the traffic card. The forwarding card is to store a number ofattributes for the subscriber connection. The forwarding card is toinclude a forwarding engine. The forwarding engine is to modify one ofthe number of attributes for the subscriber connection, while thesubscriber connection is active, without disconnecting the subscriberconnection between the computing device and the network.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention may be best understood by referring to thefollowing description and accompanying drawings which illustrate suchembodiments. The numbering scheme for the Figures included herein aresuch that the leading number for a given element in a Figure isassociated with the number of the Figure. For example, system 100 can belocated in FIG. 1. However, element numbers are the same for thoseelements that are the same across different Figures. In the drawings:

FIGS. 1A-1C illustrate systems for enabling dynamic modification of asubscriber connection, according to one embodiment of the invention.

FIG. 2 illustrates a block diagram of a network element, according to anembodiment of the invention.

FIG. 3 illustrates a more detailed block diagram of a forwarding cardwithin a network element, according to one embodiment of the invention.

FIG. 4 is a flow diagram for dynamically modifying a subscriberconnection, according to one embodiment of the invention.

DETAILED DESCRIPTION

A method and apparatus for enabling dynamic modification of a subscriberconnection are described. In the following description, numerousspecific details such as logic implementations, opcodes, means tospecify operands, resource partitioning/sharing/duplicationimplementations, types and interrelationships of system components, andlogic partitioning/integration choices are set forth in order to providea more thorough understanding of the present invention. It will beappreciated, however, by one skilled in the art that the invention maybe practiced without such specific details. In other instances, controlstructures, gate level circuits and full software instruction sequenceshave not been shown in detail in order not to obscure the invention.Those of ordinary skill in the art, with the included descriptions, willbe able to implement appropriate functionality without undueexperimentation.

References in the specification to “one embodiment”, “an embodiment”,“an example embodiment”, etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.Rather, in particular embodiments, “connected” may be used to indicatethat two or more elements are in direct physical or electrical contactwith each other. “Coupled” may mean that two or more elements are indirect physical or electrical contact. However, “coupled” may also meanthat two or more elements are not in direct contact with each other, butyet still co-operate or interact with each other.

FIGS. 1-3 show block diagrams of systems for enabling dynamicmodification of a subscriber connection, in accordance with embodimentsof the invention. FIG. 4 shows a flow diagram illustrating operationsfor enabling dynamic modification of a subscriber connection, accordingto embodiments of the invention. The operations of the flow diagram willbe described with references to the systems shown in the block diagrams.However, it should be understood that the operations of the flow diagramcould be performed by embodiments of systems other than those discussedwith reference to the block diagrams, and embodiments discussed withreference to the systems could perform operations different than thosediscussed with reference to the flow diagram.

FIGS. 1A-1C illustrate systems for enabling dynamic modification of asubscriber connection, according to one embodiment of the invention. Aswill be described in more detail below, a system 100 of FIG. 1Aillustrates a system of communications that can be based on a number ofprotocols and configurations, while a system 150 of FIG. 1B and a system160 of FIG. 1C illustrate systems of communications based on specifictypes of protocols and configurations. In particular, the system 150 ofFIG. 1B illustrates a system of communications based on a cableinfrastructure, while the system 160 of FIG. 1C illustrates a system ofcommunications based on an infrastructure that employs DSL/AsynchronousTransfer Mode (ATM) and Ethernet. These systems are by way of exampleand not by way of limitation, as other systems based on other types ofprotocols and having other types of configurations can incorporateembodiments of the invention. For example, embodiments of the inventionscan be incorporated into a wireless infrastructure, wherein wirelessconcentrators can route data from client devices into the networkelements described herein.

With regard to FIG. 1A, a system 100 comprises a computing device 102, anetwork element 104, a database server 108 and a network 110. As shown,the computing device 102 is coupled to the network element 104 through asubscriber connection 112. The network element 104 is also coupled tothe database server 108 and the network 110. In an embodiment, thenetwork element 104 is coupled to the database server 108 through thenetwork 110.

In one embodiment, the network 110 is a local area network (LAN). In anembodiment, the network 110 is a wide area network (WAN). Further, thenetwork 110 may be a combination of different networks that couple thenetwork element 104 to other computing devices and network elementscoupled thereto.

In one embodiment, the database server 108 stores data for a number ofsubscribers and their associated subscriber connections. In anembodiment, the database server 108 stores data related toauthentication, authorization and accounting for subscribers coupled todifferent network elements within a network. In one embodiment, thedatabase server 108 is a RADIUS server for storing this data regardingsubscribers and the associated subscriber connections. In oneembodiment, the network element 104 enables dynamic modification of asubscriber connection, as will be described in more detail below.

FIG. 1B illustrates a system 150 for routing data in an infrastructurefor a cable environment. Similar to the system 100, the system 150comprises the computing device 102, the network element 104, thedatabase server 108 and the network 110. The system 150 also comprises ahybrid fiber coaxial cable (HFC) network 120 and a cable modemtransmission system (CMTS) 122. As shown, the HFC network 120 is coupledto the computing device 102 and the CMTS 122. Additionally, the CMTS 122is coupled to the network element 104. Accordingly, communicationsbetween the computing device 102 and the network element 104 are routedthrough the HFC network 120 and the CMTS 122.

In an embodiment, the HFC network 120 is a cable infrastructure thatcombines the radio frequency (RF) data communications of a number ofcomputing devices 102 that are forwarded to the CMTS 122. In anembodiment, the CMTS converts the RF data communications into datapackets, such as Internet Protocol (IP) packets, to be routed by thenetwork element 104.

FIG. 1C illustrates a system 160 for routing data in an infrastructurefor a DSL and Ethernet environment. Similar to the system 100, thesystem 160 comprises the computing device 102, the network element 104,the database server 108 and the network 110. The system 160 alsocomprises a Digital Subscriber Line Access Multiplexer (DLSAM) 124, anAsynchronous Transfer Mode (ATM) network 126 and a computing device 132.

As shown, the computing device 102 is coupled to the network 104 (viathe subscriber connection 112) through the DSLAM 124 and the ATM network126. The computing device 132 is coupled to the network element 104through an Ethernet communications 134.

As is known in the art, the DSLAM 124 is a device within a network thatcombines a number of DSL communications into a single ATM transmission.The ATM network 126 comprises a number of communication links forrouting data based on the ATM protocol. Accordingly, in an embodiment,the communications from the computing device 102 is received into thenetwork element 104 as data based on the ATM protocol. Additionally, asshown, the computing device 132 and the network element 104 communicatebased on the Ethernet protocol through Ethernet communications link 134.The operations of the systems illustrated in FIGS. 1A-1C will bedescribed in more detail below.

FIG. 2 illustrates a block diagram of a network element, according to anembodiment of the invention. In particular, FIG. 2 illustrates a moredetailed block diagram of the network element 104. As shown, the networkelement 104 includes traffic cards 202-208. The network element 104 isnot limited to the number of traffic cards shown in FIG. 2, as thenetwork element 104 can include any of a number of different trafficcards. The network element 104 also includes a control card 210 and aforwarding card 212.

In an embodiment, each of the traffic cards 202-208 and the control card210 can include a processor and memory. The traffic cards 202-208, thecontrol card 210 and the forwarding card 212 are coupled to systembuses. In an embodiment, the control card 210 performs control, systemconfiguration and management tasks for the network element 104. Forexample, if the forwarding card 212 needs to be updated with a newInternet Protocol (IP) address table, such data is received by thecontrol card 210 and transmitted to the forwarding card 212, whereinsuch data is updated therein. Additionally, as will be described in moredetail below, the forwarding card 212 includes memory that storessubscriber connections for the network element 104. For example,returning to FIGS. 1A-1C, when the computing device 102 is coupled tothe network element 104, there is a subscriber connection between thecomputing device 102 and the network element 104 that includes a numberof attributes, including data rates (e.g., rate-limit and policingvalues), access control lists, etc. In one embodiment, the forwardingcard 212 updates attributes of these subscriber connections, withoutdisconnecting the subscriber connection between the computing device 102and the network element 104.

Moreover, the forwarding card 212 provides for buffering, packetprocessing and forwarding of data packets being received by the trafficcards 202-208. In particular, the traffic cards 202-208 can be coupledto a number of data transmission lines, which are coupled to othernetwork elements and/or computing devices, as shown in FIG. 1.Accordingly, the traffic cards 202-208 receive and transmit data trafficfrom and to data transmission lines coupled thereto. Such data trafficis transmitted to the forwarding card 212, where this traffic can bebuffered, processed and/or forwarded to other traffic cards within thenetwork element 104, as will be described in more detail below.

The embodiment of the network element 104 is by way of example and notby way of limitation, as network elements having other architecturalconfigurations can incorporate embodiments of the present invention.Examples of other network elements that include incorporate embodimentsof the present invention could have multiple forwarding cards or have asingle line card incorporating the functionality of both the forwardingand the controlling. Moreover, a network element having the forwardingfunctionality distributed across the traffic cards could incorporateembodiments of the present invention.

FIG. 3 illustrates a more detailed block diagram of a forwarding cardwithin a network element, according to one embodiment of the invention.In particular, FIG. 3 illustrates a more detailed block diagram of theforwarding card 212. As shown, the forwarding card 212 comprises aprocessor 310, a memory 320, a forwarding engine 302 and anauthentication/authorization/accounting (AAA) logic 304.

The processor 310 is coupled to the forwarding engine 302, the AAA logic304 and the memory 320. The forwarding engine 302 is coupled to the AAAlogic 304 and the memory 320. The AAA logic 304 is coupled to the memory320.

The processor 310 may comprise any suitable processor architecture. Theforwarding card 212 for other embodiments may comprise more processorsany of which may execute a set of instructions that are in accordancewith embodiments of the present invention. The memory 320 stores anumber of subscriber connection records 306A-I. These subscriberconnection records 306 include a number of attributes associated withthe subscriber connection, including the source address (e.g., thesource Internet Protocol (IP) address), the rate limit value, thepolicing value, the access control list, etc. The memory 320 may storealso store other data and/or instructions, for example, for theforwarding card 212 and may comprise any suitable memory, such as adynamic random access memory (DRAM) for example.

In an embodiment, the forwarding engine 302 and the AAA logic 304 areprocesses or tasks that can reside within the memory 320 and/or theprocessor 310 and can be executed within the processor 310. However,embodiments of the present invention are not so limited, as theforwarding engine 302 and the AAA logic 304 can be different types ofhardware (such as digital logic) executing the processing describedtherein (which is described in more detail below).

Accordingly, the forwarding card 212 may include a machine-readablemedium on which is stored a set of instructions (i.e., software)embodying any one, or all, of the methodologies described herein. Forexample, software can reside, completely or at least partially, withinthe memory 320 and/or within the processor 310.

The operations of dynamically modifying a subscriber connection will nowbe described. In particular, FIG. 4 is a flow diagram for dynamicallymodifying a subscriber connection, according to one embodiment of theinvention. The operation of flow diagram 400 will be described withreference to the exemplary systems shown FIGS. 1-3.

In block 402, a request to update a subscriber connection is received.With reference to the exemplary embodiment of FIG. 3, the forwardingengine 302 receives this request. In one embodiment, the database server108 transmits this request to the forwarding engine 302. In anembodiment, the application server 106 receives this request from thesubscriber and forwards this request to the database server 108. Asdescribed above, the database server 108 can store records for thedifferent subscriber connections for a number of network elements(including the network element 104). Accordingly, logic within thedatabase server 108 updates the attributes of this subscriber connectionand forwards the request to the network element 104. In an embodiment,the database server 108 transmits this request to the forwarding engine302 using the Simple Network Management Protocol (SNMP). In anotherembodiment, the database server 108 transmits this request to theforwarding engine 302 using a command line interface (CLI).

To help illustrate, a subscriber, such as a user of the computing device102, could be connected to the network element 104 through thesubscriber connection 112. Such a subscriber may want to modify theattributes, such as the current data rate, of the subscriber connection.Accordingly, the subscriber could transmit this request to update thecurrent subscriber connection to the application server 106. Forexample, in one embodiment, the subscriber could communicate thisrequest using a web page of a web site that is within the applicationserver 106. Such a web page may enable modifications to the currentsubscriber connection.

In one embodiment, the subscriber could manually generate this request.In other embodiments, this request could be dictated by the user of thecomputing device 102. For example, a first user could be an adultwherein the attributes, such as the access control list, is differentwhen compared to a second user, who is a child. Accordingly, when thefirst user logs off and the second user logs on, such that thesubscriber connection remains active, a script could be generate thisrequest to modify the attributes for this subscriber connection.

However, embodiments of the invention are not limited to the use of aweb interface and/or the application server 106 for the communication ofthis request. For example, in another embodiment, the subscriber couldcommunicate this request directly to the network element 104 without theuse of the application server 106. Moreover, requests for updates to thesubscriber connection are not limited to those request generated by asubscriber. For example, in other embodiments, a current ISP allowingfor the subscriber connection may make periodic adjustments to differentsubscriber connections. In another embodiment, the control card 210within the network element 104 may generate such a request to allow, forexample, for bandwidth balancing across of a number of subscribers, etc.

In block 404, a determination is made on whether the subscriberconnection is still active. With reference to the exemplary embodimentof FIG. 3, the forwarding engine 302 makes this determination. In oneembodiment, the forwarding engine 302 performs a lookup into the memory320 to retrieve the associated subscriber connection record 306. In oneembodiment, the request for modifications includes the source addressfor the subscriber. Accordingly, in an embodiment, the forwarding engine302 retrieves the associated subscriber connection record 306 based onthis address. In an embodiment, this is the source IP address for thesubscriber. However, embodiments of the invention are so limited, as anyother type of identification of the subscriber connection can beemployed. For example, in an embodiment, the identification of thesubscriber can be the Ethernet address for the network card within thecomputing device 102.

In an embodiment, if the associated subscriber connection record 306 islocated within the memory 320, the subscriber connection is consideredactive. In another embodiment, the subscriber connection record 306includes a field that indicates whether the associated subscriberconnection is active. Accordingly, subscriber connection records 306 mayreside in the memory 320 even when the subscriber connection is longeractive.

Upon determining that the subscriber connection is not active, theoperations of the flow diagram 400 are complete. As described above, inan embodiment, the attributes for the subscriber connection that wererequested to be updated were updated within the database server 108.Therefore, when the subscriber establishes a new subscriber connectionthese attributes will be incorporated into this new subscriberconnection.

In block 406, upon determining that the subscriber connection is active,the subscriber is re-authenticated. With reference to the exemplaryembodiment illustrated in FIG. 3, the forwarding engine 302re-authenticates the subscriber. In an embodiment, the forwarding engine302 forwards a re-authorization request for this subscriber to the AAAlogic 304.

In one embodiment, the AAA logic 304 generates a re-authenticate requestfor this subscriber that is forwarded to the database server 108.

In block 408, a determination is made on whether the re-authenticationis successful. With reference to the exemplary embodiment illustrated inFIG. 3, the forwarding engine 302 makes this determination. In anembodiment, the forwarding engine 302 determines that thisre-authentication of the subscriber is successful based on receipt ofthe attributes for this subscriber connection in response to there-authenticate request back from the database server 108. In anembodiment, the database server 108 transmits all of the attributes forthis subscriber connection to the forwarding engine 302. In anotherembodiment, the database server 108 transmits those attributes of thesubscriber connection that need to be updated to the forwarding engine302. Upon determining that the re-authentication is not successful, theoperations of the flow diagram 400 are complete.

In block 410, upon determining that the re-authentication is successful,the current subscriber connection is updated. With reference to theexemplary embodiment illustrated in FIG. 3, the forwarding engine 302updates the current subscriber connection. In an embodiment, theforwarding engine 302 updates the current subscriber connection withoutdisconnecting the subscriber connection from the network element 104.

In an embodiment, such an update message is stored into a task queue ofthe forwarding engine 302. In one embodiment, the forwarding engine 302is a single threaded process. Accordingly, the forwarding engine 302processes the different tasks stored in the task queue in an order thatsuch tasks are stored therein.

As described above, in an embodiment, the forwarding engine 302processes the packets received into the network element 104. In one suchembodiment, the forwarding engine 302 determines whether to drop datapackets for a given subscriber (whether being received from ortransmitted to) based on the data rates for this subscriber connectionstored in the associated subscriber connection record 306. For example,if a packet is received from a given subscriber connection and the datarate for this subscriber connection is beyond the limits provided in theassociated subscriber connection record 306, the forwarding engine 302drops the packet. Conversely, if a packet is received from a givensubscriber connection and the data rate for this subscriber connectionis within the limits provided in the associated subscriber connectionrecord 306, the forwarding engine 302 forwards the packet based on thedestination address stored in the packet.

As described, in an embodiment, the forwarding engine 302 is readingfrom and writing to the different subscriber connection records 306.Because in an embodiment, the forwarding engine 302 is a single-threadedprocess, there is no conflict between two different processes attemptingto access a given subscriber connection record 306. Therefore, thesubscriber connection can be dynamically updated within the memory 320of the network element 104 without having to disconnect or tear down thesubscriber connection to allow for the updates to the subscriberconnection to take effect.

In an embodiment, because the forwarding engine 302 is both forwardingpackets as well as updating the different subscriber connection records306, the forwarding engine 302 can employ a same task queue forprocessing both types of tasks, such that the forwarding engine 302processes the different types of task as based on the order in whichsuch tasks are stored into task queue. However, embodiments of theinvention are not so limited. For example, in another embodiment, onetask queue can be associated with the forwarding of packets, while aseparate task queue can be associated with the updates to the differentsubscriber connection records 306. Accordingly, the forwarding engine302 can employ a number of different types of arbitration whenprocessing the tasks from the different task queues. For example, in anembodiment, the forwarding engine 302 would only process a task from thetask queue for updating the different subscriber connection records 306when the other task queue is empty. In another embodiment, theforwarding engine 302 would process the tasks from the different tasksqueues in a N-to-M ratio. For example, in an embodiment, the forwardingengine 302 would process two tasks from the task queue for forwardingpackets for every one task processed from the task queue for updatingthe different subscriber connection records 306.

However, embodiments of the invention are not limited such that theforwarding engine 302 is a single-threaded process. In anotherembodiment, the forwarding engine 302 can be comprises of a number ofdifferent threads. In one such embodiment, in order to preclude accessconflicts to the subscriber connection records 306, the threads of theforwarding engine 302 lock the subscriber connection records 306 whenaccessing such records. For example, an update thread within theforwarding engine 302 may process the update messages received for thedifferent subscriber connection records 306, while a packet forwardingthread may process the data packets received for the differentsubscriber connections. As described, the two different threads canattempt to access a same subscriber connection record 306. For example,the update thread may attempt to update a given subscriber connectionrecord 306 to modify the policing value attribute. At a same time, thepacket forwarding thread may attempt to read the given subscriberconnection record 306 to determine whether to forward or drop thecurrent data packet for this subscriber connection.

Therefore, in an embodiment, the different threads can lock thedifferent subscriber connection records 306 such that a second threadmay have to wait for the completion of an access of a given subscriberconnection record 306 by a first thread. In other embodiments, multiplecopies of the subscriber connection records 306 can be maintained suchthat different threads access different copies of the subscriberconnection records 306 in order to preclude access conflicts.Accordingly, a separate thread can keep the different copies of thesubscriber connection records 306 up to date.

In block 412, the account for the subscriber connection is updated. Withreference to the exemplary embodiment illustrated in FIG. 3, theforwarding engine 302 updates the account for the subscriber connection.In an embodiment, the forwarding engine 302 generates an accountingmessage that includes those attributes that have been updated thataffect the account for the subscriber. For example, if the attributesupdated include the rate limit and/or policing values for the subscriberconnection, these new values can affect the cost being charged for thissubscriber connection. In one embodiment, the forwarding engine 302transmits this account message to the database server 108, where accountdata for this given subscriber connection is updated.

The servers as well as the traffic cards, forwarding cards and controlcards included in the different network elements include memories,processors and/or Application Specific Integrated Circuits (ASICs). Suchmemory includes a machine-readable medium on which is stored a set ofinstructions (i.e., software) embodying any one, or all, of themethodologies described herein. Software can reside, completely or atleast partially, within this memory and/or within the processor and/orASICs. For the purposes of this specification, the term“machine-readable medium” shall be taken to include any mechanism thatprovides (i.e., stores and/or transmits) information in a form readableby a machine (e.g., a computer). For example, a machine-readable mediumincludes machine storage media (read only memory (ROM); random accessmemory (RAM); magnetic disk storage media; optical storage media; flashmemory devices) and machine transmission media (electrical, optical,acoustical or other form of propagated signals (e.g., carrier waves,infrared signals, digital signals, etc.)); etc.

Thus, a method and apparatus for enabling dynamic modification of asubscriber connection have been described. Although the presentinvention has been described with reference to specific exemplaryembodiments, it will be evident that various modifications and changesmay be made to these embodiments without departing from the broaderspirit and scope of the invention. For example, while embodiments of theinvention are described such that a separate database server is coupledto store data related to subscriber connections. In other embodiments,such data can be stored within the network element 104. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

What is claimed is:
 1. A computer-implemented method comprising:receiving a request to modify a subscriber connection to a networkelement; and modifying attributes of the subscriber connection, within amemory of the network element, without disconnecting the subscriberconnection from the network element.
 2. The computer-implemented methodof claim 1, wherein modifying the attributes of the subscriberconnection comprises modifying a connection rate of the subscriberconnection.
 3. The computer-implemented method of claim 2, wherein thesubscriber connection is connecting a computing device to the networkand wherein modifying the connection rate of the subscriber connectioncomprises modifying the rate at which data is received into thecomputing device from the network.
 4. The computer-implemented method ofclaim 2, wherein the subscriber connection is connecting a computingdevice to the network and wherein modifying the connection rate of thesubscriber connection comprises modifying the rate at which data istransmitted from the computing device to the network.
 5. Thecomputer-implemented method of claim 1, wherein modifying the attributesof the subscriber connection comprises modifying an access control listof the subscriber connection.
 6. The computer-implemented method ofclaim 1, wherein modifying the attributes of the subscriber connectioncomprises modifying the attributes of the subscriber connection with thememory of the network element upon determining that the subscriberconnection is active.
 7. The computer-implemented method of claim 1,comprising re-authenticating a subscriber associated with the subscriberconnection prior to modifying the attributes of the subscriberconnection within the memory of the network element.
 8. Thecomputer-implemented method of claim 1, comprising updating an accountfor the subscriber connection upon modifying the attributes of thesubscriber connection.
 9. The computer-implemented method of claim 1,wherein the account is updated within a database server coupled to thenetwork element.
 10. An apparatus comprising: a memory to store anattribute of a subscriber connection between a computing device and anetwork; a forwarding engine coupled to the memory, the forwardingengine to modify the attribute of the subscriber connection, while thesubscriber connection is active, without disconnecting the subscriberconnection.
 11. The apparatus of claim 10, wherein the attributecomprises a connection rate of the subscriber connection.
 12. Theapparatus of claim 10, wherein the attribute comprises a rate at whichthe data is received into the computing device from the network.
 13. Theapparatus of claim 10, wherein the attribute comprises a rate at whichthe data is transmitted from the computing device to the network. 14.The apparatus of claim 10, wherein the attribute comprises an accesscontrol list of the subscriber connection.
 15. A network elementcomprising: a traffic card coupled to connect a computing device and anetwork through a subscriber connection; and a forwarding card coupledto the traffic card, wherein the forwarding card is to store a number ofattributes for the subscriber connection, the forwarding card to includea forwarding engine, the forwarding engine to modify one of the numberof attributes for the subscriber connection, while the subscriberconnection is active, without disconnecting the subscriber connectionbetween the computing device and the network.
 16. The network element ofclaim 15, wherein the one of the number of attributes comprises aconnection rate of the subscriber connection.
 17. The network element ofclaim 16, wherein the one of the number of attributes comprises a rateat which the data is received into the computing device from thenetwork.
 18. The network element of claim 16, wherein the one of thenumber of attributes comprises a rate at which the data is transmittedfrom the computing device to the network.
 19. The network element ofclaim 15, wherein the one of the number of attributes comprises anaccess control list of the subscriber connection.